|
|
Maybe I should reclarify. I don't think actually fully parsing the scene is
feasible anytime soon, especially with functions, but building a parse tree
is. Which would allow for manipulation of the scene language itself. This
could then be rewritten and let POV actually do the full parse to generate
the scene. I can't think of a good reason for actually evaluating the
scene.
AW
"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3DEE750B.3B747C9B@gmx.de...
>
>
> Thorsten Froehlich wrote:
> >
> > > For the most part what I need works
> >
> > Macros?
> >
>
> Functions? ;-)
>
> For a POV-Ray 3.5 compatible parser you really would need to duplicate
> half of POV-Ray to successfully parse a POV-Ray scene, even if you leave
> out textures.
>
> Christoph
>
> --
> POV-Ray tutorials, include files, Sim-POV,
> HCR-Edit and more: http://www.tu-bs.de/~y0013390/
> Last updated 15 Nov. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|